Stop Rescuing Your Team Every Single Time

Farah had not taken more than three consecutive days off in two years. In March she booked ten.

By Wednesday of the first week, her phone held eleven messages from her billing team, all versions of the same sentence: the reconciliation file won't balance, and we don't know what you usually do.

She answered four of them from a hotel lobby with her sister waiting outside. On day nine the month-end close went out three days late. A retainer client queried the invoice, the account manager escalated, and by the time Farah landed, she had a meeting in her calendar about her team's reliability.

Her director opened with a fair question: what happens to this team when you're not here?

Everyone in that room, Farah included, treated the ten days off as the cause. Cover had been thin. The handover note had been three bullets. Somebody suggested a shared runbook, and everybody nodded, and the runbook was never written because nobody in the room knew what would go into it.

The cause was six weeks earlier, and it lasted nine minutes.

Nine minutes in February

Larry, an analyst two years into the job, brought a broken reconciliation to Farah's desk. A currency field was pulling the wrong rate. He had found the symptom and wanted to know where to look next.

Farah asked him to slide the laptop over. Four screens, one mapping error, corrected, re-run. Nine minutes. Larry said thanks and walked back to his desk with a working file and no idea what had been wrong with it.

Nothing about that felt like an error. It felt like a manager helping a junior colleague under deadline. Farah got the small hit of competence you get when your hands still work. Larry got unblocked. The client got the file on time.

It happened again in March with a different field. Again in April with a different report. By May, Larry had stopped bringing the symptoms. He brought the laptop.

The signal that was sitting in her calendar

April, for Farah: thirty-one internal meetings, twenty-two of them fifteen minutes or shorter. Titles like quick look, screen share, 5 min?. Her director saw that calendar and read availability. Her team saw it and read service.

Anita Tucker and Amy Edmondson watched this exact behavior for 239 hours. Across nine hospitals, they shadowed 26 nurses and logged 194 process failures: missing medication, broken equipment, supplies that never arrived. In 93% of those problems, the nurse did whatever it took to keep patient care moving and stopped there. She walked to another ward and took their linen. She chased the drug down herself. Only 7% of responses involved telling anyone who could remove the cause.

One nurse in the study put it plainly: "Working around problems is just part of my job."

Two numbers from that paper matter here. The nurses lost an average of 33 minutes per eight-hour shift to work created by failures nobody was fixing. And 70% of the nurses interviewed believed their manager expected them to handle those disruptions alone. The patching felt like competence, which is precisely why it kept the underlying cause invisible.

Farah's team was running the same loop with one substitution. The nurse walked to the next ward for linen. Larry walked to Farah.

Look at the second number again. Nobody in that study was lazy and nobody was incompetent; the researchers noted that nurses routinely stayed forty-five minutes past the end of a shift, unpaid, to finish care. The patching was a symptom of commitment. That is what makes it so hard to see from the inside, and it is why Farah's calendar looked like a good manager's calendar right up until the week she was unreachable.

The last day it was still fixable

Rewind to those nine minutes. Same problem, same deadline, same February afternoon, and one change: Farah's hands stay off the keyboard.

"Walk me through what you checked."

Then: "Open the mapping table. What's in row 40?"

Then the hardest part, which is saying nothing for eleven seconds while he reads it.

This version basically takes twenty-two minutes. Thirteen more than the fix she actually did, once, in February. Larry keeps it, and the March problem never reaches her desk.

The dynamic has an older name than any of this. Stephen Karpman, a San Francisco psychiatrist, mapped it in 1968 as the ​drama triangle: victim, persecutor, rescuer, three roles people slide between in stuck situations.

The rescuer is the one that looks healthy from the outside. Karpman's argument was that every role in the triangle discounts somebody's capability, and the rescuer discounts the capability of the person being rescued.

What to do when the next one lands on your desk

Here’s what you do the next time:

• Keep a rescue log for two weeks. Date, who came to you, what they needed, minutes you spent, and whether you have seen that class of problem before. Nothing else. Farah's log would have shown Larry six times in six weeks, four of them mapping errors. That pattern is invisible in a calendar and obvious in a log.
• Set a floor on the keyboard. If a fix takes under fifteen minutes, you have room to talk someone through it. The extra ten minutes is the entire investment. Spend it while you're still in the room.
• Change the question you answer. When someone arrives with a problem, ask what they have already tried and what they would do if you were on a flight with no signal. Then wait. The silence will feel long to you and useful to them. The urge to fill it arrives at about four seconds. Hold to eight.
• Name the successor out loud for one recurring task. Not a delegation plan, not a RACI, one sentence in a team meeting: from now on Larry owns currency mappings, and if it breaks, he decides. Then let a broken one reach him first. Farah's instinct will be to check the file before it goes out. Checking it is the same nine minutes wearing a different coat.
• Take the biggest repeat on your log and kill it where people can watch. One afternoon, the cause, with whoever keeps hitting it sitting next to you. In 1990 Acey Choy proposed a replacement for Karpman's three roles, and the ​rescuer becomes a coach: someone who offers real support and leaves the problem in the other person's hands. That afternoon is what the swap looks like in practice.

Your version of this

You already know which of your people has stopped bringing you the symptom and started bringing you the laptop. You probably know the exact recurring problem, too, because you've fixed it four times and never once looked at where it comes from.

Farah's ten days off were fine. Her February was the problem. Don’t let it happen to you.